Credential Format
Name
AnonCred
Implementation Support
Specification
Standardization (Body, Process)
Community Spec (draft)
Encoding Scheme
JSON
Rich Schemas-Semantic
false
Crypto Agility
false
Selective Disclosure
true
Predicates
true
Compatibility with Signing Algorithms
CL
Compatibility with Key Management Methods (Issuer)
did:indy, did:cheqd
Signing Algorithm
Name
CL
Implementation Support
Hyperledger Ursa, https://github.com/privacybydesign/gabi
Specification
CL-Signatures of there own do not have a formal specification, that is included in Anoncreds
Standardization (Body, Process)
none
Recognition by government authorities (NIST, BSI, ...)
false (not acknowledged (independent crypto analysis published))
Performance
Ursa: up to 7 seconds for a validation and approximately 30 seconds for credential definition generation; IRMA (Yivi): both in less than a second
Hardware support
false
Unlinkability-Uncorrelatability-Blind signatures possible
true
Security strength
equivalent to RSA2048
Post-quantum security
false
Status Algorithm
Name
Indy Revocation
Implementation Support
Indy SDK
Standardization (Body, Process)
AnonCreds
Recognition by government authorities (NIST, BSI, ...)
false
Category
Accumulator
Observability
false
Scalability
false (limitations by accumulator size)
Key Management (Issuer)
Name
did:web
Implementation Support
Infrastructure for Key Resolution
true (web server)
Key Rotation
true
Key History
false
Party
holder, issuer
Key Management (Holder)
Name
link secrets
Infrastructure for Key Resolution
false
Key Rotation
false
Key History
false
Party
holder
Issuance Protocol
Presentation Protocol
Trust Management
Name
Verifier knows Issuers
Implementation Support
Manual / bespoke
IPR Policy
None
Standardization (Body, Process)
None
Specification
None
Description
The verifier knows which issuers he trusts for issuing certain credentials, organizational solution